chore(ci): update all GitHub Actions to latest majors - #239
Merged
Conversation
Bumps every action used by pr.yml and release.yml to its current latest release: actions/checkout v6 -> v7 (v7.0.1) actions/setup-node v6 -> v7 (v7.0.0) actions/cache v5 -> v6 (v6.1.0) actions/upload-artifact v6 -> v7 (v7.0.1) actions/download-artifact v7 -> v8 (v8.0.1) astral-sh/setup-uv v8.0.0 -> v9.0.0 pypa/gh-action-pypi-publish stays on @release/v1 — that's the moving ref upstream recommends and it already resolves to the newest v1 (v1.14.2); there is no v2. Breaking changes reviewed against actual usage — none bite: - checkout v7 blocks checking out fork PRs under `pull_request_target` / `workflow_run`. Neither workflow uses those triggers (pr.yml is `pull_request`, release.yml is `workflow_dispatch`). - setup-node v7 stops exporting the dummy NODE_AUTH_TOKEN placeholder. This helps the publish-npm job, which uses OIDC Trusted Publishing — the placeholder could previously pollute .npmrc during OIDC publish. - download-artifact v8 now errors instead of warning on a digest mismatch, and skips decompressing non-zip downloads. Our artifacts are uploaded with the default `archive: true`, so they still unzip normally; the stricter digest check is a straight win. - cache v6, upload-artifact v7 and the rest of setup-node v7 are ESM migrations with no behavioural change for these call sites. One deliberate behaviour change: setup-uv v9 flips `prune-cache` to false by default, so the uv cache keeps prebuilt wheels instead of re-fetching them from PyPI each run. Faster CI at the cost of a larger cache entry — all jobs share one key (hash of UV_CACHE_GLOB), so this is a single entry growing, not one per job. Left at the new default; set `prune-cache: true` if repo cache pressure ever becomes an issue. Verified: actionlint clean on both workflows, YAML parses. Claude-Session: https://claude.ai/code/session_01KzBTj2GWBXhG8gbTorDYjW
Deploying simple-module-python with
|
| Latest commit: |
d524237
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e579adb4.simple-module-python.pages.dev |
| Branch Preview URL: | https://chore-update-gh-actions.simple-module-python.pages.dev |
antosubash
marked this pull request as ready for review
August 6, 2026 08:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps every action used by
pr.ymlandrelease.ymlto its current latest release.actions/checkoutv6v7(v7.0.1)actions/setup-nodev6v7(v7.0.0)actions/cachev5v6(v6.1.0)actions/upload-artifactv6v7(v7.0.1)actions/download-artifactv7v8(v8.0.1)astral-sh/setup-uvv8.0.0v9.0.0pypa/gh-action-pypi-publish@release/v1Floating-major pins kept for
actions/*and the exact pin kept forsetup-uv, matching the existing convention in these files.Breaking changes, checked against actual usage
pull_request_target/workflow_run. Neither workflow uses those triggers (pr.ymlispull_request,release.ymlisworkflow_dispatch), so this is inert here.NODE_AUTH_TOKENplaceholder. This helps thepublish-npmjob, which uses OIDC Trusted Publishing — the placeholder could previously pollute.npmrcduring an OIDC publish.archive: true, so they still unzip normally; the stricter digest check is a straight win.setup-uv v9:
prune-cachenow defaults tofalseLeft at the new default. Measured on this PR's run rather than guessed:
-pruned-from it makes the first run a cold miss. All parallel jobs then race to populate the new key; one wins and the rest log##[warning] Failed to save: Unable to reserve cache ... another job may be creating this cache. Benign, non-fatal (every job still passed, and the winner loggeduv cache saved with key: ...), and it disappears once the key is warm.No reason to override with
prune-cache: true.Verification
actionlintclean on both workflows (exit 0); both parse as YAMLPR checksgate — run 31084586499. Sincepr.ymlis the file being changed, this run is the test.Draft so you can eyeball it before marking ready.
https://claude.ai/code/session_01KzBTj2GWBXhG8gbTorDYjW